<text>COPYING & COMPARING IMAGESThe Copy Image option allows you to copy all or part of a premastered image to another medium. You can copy a premastered image from: - DATA/DAT tape - WCD-ROM hard disk image - disk file - CD-ROMto one of the following media: - DATA/DAT tape - WCD-ROM hard disk image - disk fileThis feature is useful for example in copying the premastered image from tape to a disk file. The mastering plants accepting DATA/DAT tapes in fact use this utility to transfer your CD-ROM image from the DAT cartridge to their replication systems.When you select this option, RomMaker will ask you to specify the source and destination of the image you wish to copy.RomMaker will read the volume header information from the source CD-ROM image and display this on the screen. If the data does not conform to an ISO 9660 or Hi-Sierra image, an error will be reported since this utility can only be used to copy legitimate CD-ROM images from one media to another.The Compare Image option looks through each file and folder on the images being compared and indicates any files that have have different sizes or attributes on one image than their counterparts on the other image. You should run this compare operation on your virtual CD-ROM image after testing but before making the DAT tape. This process can catch any changes that may have occurred to your files after testing completed.FORMAT WCD-ROM HARD DISKIf you purchased a WCD-ROM subsystem, it will have come prepared so that you can immediately start making inhouse CD-ROMs. Occasionally while moving the tower unit or simply because of hard disk failure, you may need to re-prepare the WCD-ROM subsystem. This utility initializes the WCD-ROM subsystem so that RomMaker can use it to produce your CD-ROM's.If you select this option, you will get a warning notice that any data on the WCD-ROM system will be destroyed after which the system will commence a low level initialization of the subsystem. In addition to other system level operations, this process also reformats your hard disk so that any bad sectors are blocked out from future access.You will rarely need to perform this operation, though it is a good idea to re-initialize the WCD-ROM subsystem once every year so that bad data blocks are masked out of regular use.GENERATE CD-ROM DRIVE CHARACTERISTICSThe RomMaker emulation feature mimics a physical CD-ROM in performance by using an algorithm that simulates the behavior of an actual CD player even though the files are coming off a hard disk. This algorithm is used to determine how much delay would have occurred had you been using an actual CD-ROM.Each time you use the emulator, the drive characteristic algorithm is also loaded so that you will get a true feel of how the application you are testing will run on a CD-ROM if you were to produce the CD-ROM. Each time a read request is made to the emulator, it analyzes the request to see where the CD-ROM drive head would have been positioned and delays the read request to the hard disk file appropriately. This algorithmic delay in hard disk access to the translated file provides you with a sophisticated quality assurance capability without actually producing a CD-ROM.RomMaker comes with a set of characteristics to mimic the performance of the commonly available CD-ROM drives. However, given the number of CD-ROM drives already available and the continuing introduction of new models, you may need to build a new algorithm for a drive not in our supplied list. This option allow you to generate the characteristics algorithm for your drive by running a test pattern on a particular CD player. To generate a new characteristic, follow these steps:1) Hook up the CD-ROM drive that you want to mimic to your Macintosh. Verify that you can insert a CD-ROM into the drive and read it normally.2) Insert any fully populated (500MB or greater) ISO 9660 or Hi-Sierra compliant CD-ROM available to you into your CD-ROM drive.3) Run RomMaker and choose "Generate CD-ROM drive characteristics..." from the Emulate menu. You will be asked for a name for RomMaker to associate with this drive type; enter any name you like and click OK.RomMaker will then run a test pattern on the CD-ROM drive. This test takes about half an hour and can be cancelled if necessary. When the test is complete, you will be returned to the title form for further action.Note that all title files will not automatically use the new drive characteristics you have just created. You will need to go to the Misc Options section of the title file and specify which drive characteristics to use on a title-by-title basis.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>15</text>
</content>
<name>Utilities</name>
<script></script>
</card>
card_35540.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he Examine mehu allows you to view and modify the contents of several text files created and maintained by RomMaker. RomMaker comes with a built-in text editor; however, if you want to use another one, just make a copy of it, name the copy "Text Editor", and put it in the folder with RomMaker. The next time you use the Examine menu, RomMaker will open your editor instead of its own.IMPORTANT NOTE: RomMaker's built-in editor cannot read more than 30,000 bytes from a file; thus if it used to save a very long file, the file will be truncated to 30,000 bytes when saving.ROM CONTENT FILEThis option displays the ROM Content file specified by the currently open title file.USAGE STATISTICS FILEThis option displays the usage statistics file most recently generated by emulating using an image created using the currently-open title file.LOG FILEThis option displays the most recent log file for the current title file. Whenever RomMaker completes a successful Make Rom operation, it produces a log file containing the names and physical locations of each file on the CD-ROM. This file is created in the "LOG" folder within the RomMaker folder, and its name is the volume label specified in the title file, followed by ".LOG", unless otherwise specified in the "Misc Options" section of the title file. The log file contains the name, absolute physical location, size, and attributes for each file placed on the CD-ROM. Here's a sample log file:</span><span class="style5">====================================================================== STATISTICS FOR CD-ROM VOLUME SET 'US__NGA_' Produced: Mon Jul 13 15:06:58 1992 Total number of CD-ROM Sectors: 2506 First CD-ROM record address: 00:02:00 Last CD-ROM record address: 00:35:30====================================================================== Layout of Volume :'US__NGA_' Creation Started : Mon Jul 13 15:05:35 1992 Finished : Mon Jul 13 15:06:58 1992Data Rsrc Audio Loc File SizeSector Sector (mm:ss:ff) Data Rsrc Date/Time Stamp Attribs------ ------ ------------- ------ ------- --------------- -------HD:picture library ->:FOLDER:PICTUREL.IBR 118 118 00:03:43 3248 0 14 Jun 92 23:52:34 'r*'HD:compare disks 10/11/90 ->:FOLDER:COMPARE_.DIS 123 123 00:03:48 0 108711 17 Feb 92 11:32:37 'r*'HD:comparison results ->:FOLDER:COMPARIS.ON_ 178 178 00:04:28 2271 0 27 Jun 92 12:23:23 'r*'</span><span class="style1">...ERROR FILEThis option displays the error file (if any) generated while making the last RomMaker image.A significant class of errors can occur when the ROM Content File is being processed by the RomMaker. These errors usually arise from improper syntax and/or filenames. When you make an image, RomMaker reads the layout or backup script file associated with the title and checks for errors before building the image directory and file structures.RomMaker displays an error window as soon as it encounters the first error. One choice in this error window is to send this and subsequent errors to an error file. If you choose this option, an error file is created in the "LOG" folder within the RomMaker folder. Its name is the same as the ROM Content File, followed by ".ERR", unless specified otherwise in the "Misc Options" section of the title file.RomMaker will record up to 50 errors before aborting processing.</span></text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>14</text>
</content>
<name>Examine</name>
<script></script>
</card>
card_35226.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">MULATING APPLE & ISO VOLUMESRomMaker provides a unique capability of verifying that you have created the correct CD-ROM before sending it to the mastering plant. Emulation instructs RomMaker to present the image on the Macintosh desktop as if it were a normal CD-ROM. You can choose to emulate either Apple HFS or ISO 9660 volumes, using either the Data-DAT or the RomMaker hard disk as a source image.After choosing one of the above emulation options, the CD-ROM icon will appear on your desktop, and will behave just as a normal CD-ROM would. Use whatever validation process you would with the real CD-ROM to satisfy yourself of the image's worthiness for mastering. You can even share files on an ISO image with a DOS machine over the network (assuming your network supports such an operation).If you created your CD-ROM image using the combined HFS/ISO standard, you can emulate either standard, but only one at a time.COLLECTING & REPORTING USAGE STATISTICSThe emulation feature maintains statistics for each file on the CD-ROM image. These statistics can help you refine the performance of your CD-ROM through better software design, as well as appropriate rearranging of the directory structure, by giving you information on the usage patterns encountered during the emulation session. Information tracked includes:- Number of file opens per file. This helps you determine whether your application is doing too many file opensΓÇöa CD-ROM function that is particularly costly in terms of access and processing times.- Number of file reads. This indicates how many distinct read requests were sent to the CD-ROM while you were running a particular test or application. This helps you determine the optimum layout of files on a CD-ROM. Files that are read and accessed most often should be placed where access times are the fastest, which is close to the inner part of the CD-ROM.- Average access time for file reads. This indicates how the CD-ROM is physically being accessed. If the average access time is high, the file is being accessed by the head moving significant distances - that is, the application is reading data from one file and jumping across a large number of tracks to access other files. For optimum performance, files that are read most frequently should be positioned not only close to the inner part of the CD-ROM, but also close to each other.To collect these statistics, follow these steps:1) Create a CD-ROM image, then use the appropriate Emulate menu item.2) Choose "Start collecting usage statistics" from the Emulate menu.2) Run your test or application as if you were testing an actual CD-ROM.3) When testing is finished, choose "Report usage statistics" from the Emulate menu. RomMaker will sort the collected statistics based on number of file reads and then output them to the Usage Statistics File.4) Choose "Usage Statistics File" from the "Examine" menu. RomMaker will display the statistics file (which will have been created in the "LOG" folder within the RomMaker folder, unless otherwise specified within the Misc Options section of the title file).Here's a sample usage statistics file:</span><span class="style5"> Volume Label: SAMPLE Produced @ Thu May 23 15:31:15 1991 File File Tot. Seek Avg. Seek Reads Opens Time(sec) Time(msec) CD-ROM FileName _____ ______ __________ __________ __________________________ 00005 000001 0000000001 0000000166 :MyFolder:picture library 00005 000001 0000000001 0000000155 :MyFolder:disk verify 00005 000001 0000000001 0000000166 :MyFolder:disk comparer 00005 000001 0000000001 0000000144 :MyFolder:interest calculator 00005 000001 0000000001 0000000155 :MyFolder:system modes 00004 000001 0000000001 0000000166 :bibliographic file</span><span class="style1">This shows some sample statistics on a test run carried out for an application which opened some files on a CD-ROM. Note that the statistics system does not report any files which have had zero activity; i.e., no file opens and no file reads. The system designer should look at those files carefully as the application appears not to be using these files. Such files are often just remnants of an older system and need to be discarded.After determining from the usage statistics file which CD-ROM files need to be moved closer to one another, you can edit the ROM Content File to change the order in which they will be put on the CD-ROM, since RomMaker processes and copies files in order that they are encountered in the ROM Content File. Often, simply rearranging the ROM Content File is all you need to do to optimize the performance of your CD-ROM.ALLOW CHANGES TO CURRENT IMAGEThis option allows you to make certain changes to the ROM image's desktop appearance. You may change: - icon positions within a window - folder window sizes and positions - whether folders are open or closedYou should NOT: - rename or delete any item (file or folder) - move any item from one folder to another - alter the contents of any fileAlthough certain of the "forbidden" changes might appear to be allowed, such changes will NOT be saved in the image and may lead to RomMaker processing errors.</span></text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>13</text>
</content>
<name>Emulate</name>
<script></script>
</card>
card_34915.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>DATA-DAT IMAGEThis option creates an "image" of your CD-ROM on magnetic tape by instructing RomMaker to process the current title file (and the associated ROM Content File), thereby copying all relevant files and folders to the DAT tape in such a way that it is a byte-for-byte copy of the eventual CD-ROM. After creating such an image, you can test it by using the Emulate menu.WCD-ROM HARD DISK IMAGEThis option creates an "image" of your CD-ROM on the RomMaker hard disk by instructing RomMaker to process the current title file (and the associated ROM Content File), thereby copying all relevant files and folders to the DAT tape in such a way that it is a byte-for-byte copy of the eventual CD-ROM. After creating such an image, you can test it by using the Emulate menu.CD-ROM FROM WCD-ROM HARD DISK IMAGEThis option replicates the pre-mastered image stored on the WCD-ROM hard disk to a blank CD-ROM in the WCD-ROM drive (thus permanently using up the blank CD, so you probably shouldn't do it until you've tested the image thoroughly using RomMaker's Emulate features).ICON-ONLY IMAGEThis option helps create polished Apple HFS CD-ROMs by allowing you to set up your CD-ROM's desktop information (window positions and sizes, icons, etc) once, just as you want it, and then save that information for later use by RomMaker. You then don't need to worry about accidentally shifting one of your "original" icons or windows and having a subsequent CD-ROM inadvertently reflect the change.The icon-only image, RomMaker processes the ROM Content File just as it does when making any other type of image, but it doesn't actually transfer any data from within the files it encounters. Instead, it creates a special kind of image in which the desktop information is present but none of the files contain any information. The windows and icons in this special image can be positioned by clicking and dragging just as if it were a normal Macintosh disk. When all the files, folders, and windows are positioned as you want them to be, use the "Make Icon Database..." option (see below) to save this information so that RomMaker can use it when making your actual CD-ROM.ICON DATABASE FROM ICON-ONLY IMAGEOnce you have created and adjusted an icon-only image (see above) to your satisfaction, use this option to save the image's desktop information to a file that RomMaker can use when creating subsequent CD-ROM images. (Unless you specify otherwise in the "Misc Options" section of the title file, this file will be saved in the "DFN" folder within the RomMaker folder using the name of your volume followed by " ICON DB" (note the two spaces) as the the filename.)</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>12</text>
</content>
<name>Make</name>
<script></script>
</card>
card_34318.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text> Make Data-DAT Image WCD-ROM Hard Disk Image CD-ROM from WCD-ROM Hard Disk Image Icon-only Image Icon Database from Icon-only Image Emulate Emulating Apple & ISO Volumes Collecting & Reporting Usage Statistics Allow Changes to current image Examine Utilities Copying & Comparing Images Format WCD-ROM Hard Disk Generate CD-ROM Drive Characteristics</text>
</content>
<content>
<layer>card</layer>
<id>2</id>
<text>For information on a menu item, click it.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>11</text>
</content>
<name>RomMaker Menus</name>
<script></script>
</card>
card_34092.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">ach CD-ROM that you publish must have its own title file and ROM Content File. The content specification phase of creating a CD-ROM requires you to create an ASCII text script file, using either your own editor, say Teachtext or the editor supplied with RomMaker. RomMaker requires all Rom Content script files to be in ASCII text format. Hence, if you use your own editor, all script files must be saved as ASCII text.Syntax of the ROM Content file:For each file or folder that you want to put on a CD-ROM, the content specification script must contain a single-line entry containing the following information: ΓÇó The name of the source file/folder on your hard disk or network. This tells RomMaker where to look for the files when making the CD-ROM. ΓÇó The name of the destination file/folder on the CD-ROM. This tells RomMaker where to put the file on the CD-ROM and what to call it.Each content entry has the following structured textual format: "Source File/Folder Name" "CD-ROM File/Folder Name" <Optional Flags>The Rom Content script format mandates that each line must have a source filename and a CD-ROM filename. RomMaker will flag an error for each line which doesn't meet this requirement. For example, if you specify a line where the source file resides on an unknown disk, RomMaker will signal an error since it cannot find the file. This feature is particularly important in network environments, where you may have specified a Rom Content file with network files but have not yet connected to it.There are two mandatory paramaters and one or more optional parameters (called flags) you must specify for each file/folder you wish to put on a CD-ROM. As an example, suppose you wanted to make a simple CD-ROM containing just two files - the source file 'Home' is to be called 'Home Stack' in the root folder of the CD-ROM and the file 'Hypercard' is to be placed in the folder 'Applications' on the CD-ROM. Let us say that both these files reside on our 'Macintosh HD' volume inside the 'Card' folder. The content specification file would contain the following two textual lines which you would input: "Macintosh HD:Card:Home" ":Home Stack" "Macintosh HD:Card:Hypercard" ":Applications:Hypercard"Note the use of the double quote delimiter to separate the source file name and CD-ROM file name token. Since an Apple filename can contain space and other non alphanumeric characters, the double quote delimiter is used to specify the bounds of the source filename and destination filename.In the above example, the files 'Home' and 'Hypercard' located in the 'Card' folder on the volume 'Macintosh HD' will be copied to the CD-ROM. The file 'Home' will be moved to the root of the volume and renamed 'Home Stack' on the CD-ROM while the file Hypercard will be resident under a folder on the CD-ROM called 'Applications'. This process of specifying files can be cumbersome if you have to individually specify every file that goes into the CD-ROM. However this is not usually the case since it is likely that your source files are orgainzed into some logical structure and you will in fact be copying groups of files located in specific folders. You can use the scripting system to specify a set of files per line. For example, suppose you wanted to transfer all the files in your CARD folder to a CD-ROM folder called 'Hypercard' folder on the CD-ROM. The content definition file would contain the following entry: "Macintosh HD:Card" ":Hypercard"RomMaker will search the 'Card' folder of the volume 'Macintosh HD' for each file and put those files into the 'Hypercard' folder on the CD-ROM. You can also copy complete folder trees using a single line specification in your content specification file. To illustrate, suppose you want to make a copy of two of your volumes 'Macintosh HD' and 'Second Volume' on a CD-ROM. Your Rom Content file would contain the following line: "Macintosh HD:" ":Primary Volume" -f "Second Volme:" ":Secondary Volume" -fThe '-f', called the 'folder' flag, tells RomMaker that you want to copy the volume/folder 'Macintosh HD:' in whole with any files or folder underneath the root folder to a CD-ROM folder structure whose top is the folder 'Primary Volume'. The second line in the content specification file simply copies the volume 'Second Volume' to the CD-ROM folder 'Secondary Volume'. In a later section, we will see how other flags can be helpful in specifying other attributes such as hide files/folders or timestamp. Note that these flags are optional.RomMaker ignores all lines that begin with a semi-colon ';'. Use this feature to insert comments in your Rom Content file as documentation.Each Rom Content file entry can contain one or more flags that further define the file attributes of both the source file and the file to be put on the CD-ROM. Note that each flag will only be valid for the file specification on that line. As soon as RomMaker encounters a new script line in the Rom Content file, it automatically reverts to the default attributes specified in the title form.The general format of a flag is the '-' character, followed by a </span><span class="style7">lower case</span><span class="style1"> letter which defines the flag, followed by one or more parameters. The following flags are legal: </span><span class="style8">-f</span><span class="style1"> The -f or subfolder flag searches the folder tree for all files matching the input file specification. The following command will cause RomMaker to copy all files and folders under the folder 'Doc Data' to a CD-ROM folder 'CD Doc Data': "Macintosh HD:Doc Data" ":CD Doc Data" -f </span><span class="style8">-t</span><span class="style1">The -t or timestamp flag followed by a date and time defines the date and time stamp for the group of files defined by the source file specification. The following command will cause RomMaker to copy the file 'RomMaker Doc" to the CD-ROM root with its time stamp set to December 31st 1990 at 12:00pm: "HD:Doc:RomMaker Doc" ":" -t 12\31\90 12:00 </span><span class="style8">-o</span><span class="style1">The -o or output file flag, followed by one of the attribute types 'n' or 'h', sets the attributes of the output file created on the CD-ROM. On a CD-ROM, you can have normal or hidden files; system files aren't applicable and the read-only flag is always set due to the physical properties of a CD-ROM. The n [normal] or h [hidden] attribute selector overrides any title defaults. The following command will cause RomMaker to copy and hide the file PASSWORD in the CD-ROM root folder: "HD:Password" "Password" -oh</span><span class="style8">-k</span><span class="style1">The -k or keep flag is used to keep the date and time stamp of the original source file. When RomMaker makes a CD-ROM, it uses the defaults specified in the title form for the files as its date and time stamp if you turned the 'keep' attributes check box off. The -k flag lets you override this and keep the original time stamp on specific files/folders. To keep the timestamps on all files, use the Keep Timestamp option in the title form (instead of flagging each line in your Rom Content file).</span><span class="style8">-m</span><span class="style1">The -m or marked flag is used to exclude files from a particular search path. To illustrate, suppose that you have folder tree containing some 2000 files and 100 directories most of which you wish to place on a CD-ROM but wish to exclude say 10 folders/files from this search path. The -m or marked flag tells the RomMaker to ignore all filenames/folders whose first and last character of the name are '(' and ')' respectively. Hence all you have to do is to go and bracket the names of the files/folders using the finder and use the -m flag in your script file. For example, suppose you have a folder 'Rom Data' that contains a file called 'Dont Want' which is not be placed on the CD-ROM. You would change the name of this file to '(Dont Want)' and then script the following line in your Rom Content file. "HD:Rom Data" ":Rom Data" -f -mThe -m instructs RomMaker to ignore all files/folders whose first character is '(' and last character is ')';</span><span class="style8"> -v</span><span class="style1">The -v or version flag is used if your source of data is an ISO 9660 CD-ROM. The filenames on these CD-ROMs have a version number appended to their name. For example, the file "MYFILE.TXT" will show up as "MYFILE.TXT;1" when mounted on a Macintosh. This flag simply instructs the RomMaker to remove the version number from the filename when it puts it out on the HFS CD-ROM. </span><span class="style8">-i</span><span class="style1">The -i or icon flag enables you to specify an icon for the CD-ROM you make. System 7 allows you to define an Icon for any CD-ROM. To enable this feature, simply create a file containing the icon using ResEdit and then specify this file in the script with the -i flag. e.g. "HD:CDROM Icon" -i "Source:Folder" ":Rom Folder" -f ... ...Note that if you are copying a complete hard disk volume which has its own icon, RomMaker will automatically copy that icon to the CD-ROM image unless it finds a script line with the -i flag.When RomMaker sees the -i flag, it simply opens up the file's resource fork and uses the first icon it finds in the resource fork as the Volume Icon for the CD-ROM. Hence to create a CD-ROM icon, simply create a file using ResEdit and insert the Volume Icon you want into that file. Then specify that file in your script and RomMaker will do the rest.</span><span class="style8">-x</span><span class="style1">The -x or exclude flag is used only in dual mode CD-ROMs which have both the ISO and Apple HFS file systems on the same CD-ROM. Since a dual mode CD-ROM has two partitions, you may wish to select whether a set of files/folders need to be excluded from a particular file system. The format for this is demonstrated below: "HD:Mac folder" "Mac folder" -f -x ISO "HD:DOS folder" "DOS folder" -f -x HFS "HD:Both folder" "Both folder" -fIn the above script, the first line in the script uses the -x (exclude) flag to instruct the RomMaker not to enter these files into the ISO 9660 file system partition since they are clearly Macintosh files. In the second line, the -x flag is used to ensure that the files are not found in the HFS partition. The last line where no -x flag is found (the default) means that the files in that folder are found in both partition.When a dual mode CD-ROM is made, a particular file is copied only once and both the file system entries point to just this once occurrence of the file on the CD-ROM. As a result, if the files are common to both Apple HFS and ISO 9660, each partition appears to hold the maximum allowed per CD-ROM, upto 680MB of data. You can have as many flags as you want on each command line. For example, the Rom Content script line "Mac HD:Secret Folder" ":Password" -oh -t 01\01\91 12:00 -f -k -mwill search the folder tree under 'Secret Folder' for all files excluding all marked files and copy them to the 'Password' folder on the CD-ROM where all the files are hidden and timestamped January 1, 1991 12:00 pm.By combining optional flags on each Rom Content file entry, RomMaker supports a powerful mechanism for building your CD-ROM folder structure efficiently and to your satisfaction.</span></text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>10</text>
</content>
<name>ROM Content File</name>
<script></script>
</card>
card_33915.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>WHEN EMULATINGWhen RomMaker uses a disk or tape image to emulate a CD-ROM, it needs to know which physical CD-ROM drive it should mimic. This field allows you to specify the physical drive to emulate on a title-by-title basis. RomMaker comes with a set of drives whose characteristics are known; you can pick from one of this set or generate your own characteristics file using the "Generate CD-ROM drive characteristics..." item in the "Emulate" menu.USAGE STATISTICS FILEThis field allows you to specify where RomMaker will create the next usage statistics file for this title file. If you leave this field blank, the file will be created in the "LOG" folder within the RomMaker folder, and will have the same name as the volume name, followed by ".STAT". For more information on the usage statistics file, see the help section on the Emulate menu.LOG FILEThis field allows you to specify where RomMaker will create the next log file for this title file. If you leave this field blank, the file will be created in the "LOG" folder within the RomMaker folder, and will have the same name as the volume name, followed by ".LOG". For more information on the log file, see the help section on the Examine menu.ERROR FILEThis field allows you to specify where RomMaker will create the next error file for this title file. If you leave this field blank, the file will be created in the "LOG" folder within the RomMaker folder, and will have the same name as the volume name, followed by ".ERR". For more information on the log file, see the help section on the Examine menu.ICON DATABASE FILEThis field allows you to specify where RomMaker will create the next icon database file for this title file. If you leave this field blank, the file will be created in the "DFN" folder within the RomMaker folder, and will have the same name as the volume name, followed by " ICON DB" (note the two spaces). For more information on the icon database file, see the help section on the Emulate menu.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>9</text>
</content>
<name>Misc Options</name>
<script></script>
</card>
card_33704.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">OLUME ATTRIBUTESEach CD-ROM must have a CD-ROM creation date and time stamp. However, it may also have a date and time modified field, which specifies the last date and time the volume was modified. This field typically contains the same data as the date and time created field, but may be different if for example you decide to issue an update to a previously created CD-ROM. Most applications do not use this field.</span><span class="style2">Expiration Date & Time</span><span class="style1">This field tells the retrieval software when this CD-ROM becomes obsolete. DOS ignores this field; it is for use by your retrieval software. This field is sometimes used in regular publishing applications where the most recent CD-ROM must be used. The retrieval software would, in such a case, check the expiration date on the CD-ROM and tell the user that this CD-ROM had become obsolete.</span><span class="style2">Effective Date & Time</span><span class="style1">This field tells the retrieval software when to activate this CD-ROM; it complements the expiration date and time. For a regular publishing cycle, this field would typically be set to the expiration date and time of the previous CD-ROM in the series.FILE & FOLDER ATTRIBUTESRomMaker allows you to control two attributes for each file and folder that it creates on the CD-ROM: Visible/Hidden, and the file/folder creation date & time.</span><span class="style2">Keep/Override</span><span class="style1">If you don't need to control the attributes on your CD-ROM files & folders, use "Keep attributes..."; otherwise, use "Override..." to instruct RomMaker to use the specified attributes. You can even override the override for any particular file or group of files, by using the optional "-k" flag in the appropriate line of the ROM Content File (see ROM Content File Format).</span><span class="style2">Hidden</span><span class="style1">Using this option instructs RomMaker to force all files/folders on this CD-ROM to be hidden, meaning they won't show up when the browsing the CD-ROM after it is produced. (Some CD-ROMs use this feature as a crude form of protection against illegal access by hiding all folders. Note, however, that there are several tools available that will display such files and folders, so this is not a very secure protection method.)If you want most but not all of your files/folders to be hidden, the ROM Content File format allows you to override this option line-by-line as well (see ROM Content File Format).</span><span class="style2">Date and Time</span><span class="style1">These attributes apply to all files and folders created by RomMaker. If you leave these unfilled, the values in the volume creation and date and time fields are used.</span></text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>8</text>
</content>
<name>Date, Time, & Attributes</name>
<script></script>
</card>
card_33363.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>VOLUME SET IDENTIFIERThis parameter identifies the volume set that this CD-ROM belongs to. ISO allows you to produce multiple CD-ROMs that belong to the same volume set. This field is used to identify the volume set for this CD-ROM.SYSTEM IDENTIFIERThis specifies the name of a system that can act on the contents of a reserved area of the CD-ROM called the System Area (which we will examine shortly); you can use up to 32 characters. The system identifier is used in identifying the software system that can understand how to interpret the system area of the CD-ROM.APPLICATION BLOCK FILEThis specifies a file on your hard disk or network whose contents will be copied into the Application Use area of the CD-ROM volume identifier. Each volume identifier on a CD-ROM contains 512 bytes where you can put any information in any format. RomMaker allows you to insert that information into this area via a file (ASCII or binary) which contains 512 or fewer bytes. RomMaker enforces this size rule by preventing you from specifying a file larger than this limit.SYSTEM AREA FILE(Note: The System Area file is ignored for all ROM Standard settings except ISO 9660.) Each CD-ROM volume has 16 physical sectors (Sectors 0 to 15) located at the start of the CD-ROM which are reserved for special system use. Unlike the ISO-9660 file structure where data is related via directory and file entries, this area is physically identified by the sector number and contains 32768 or fewer bytes of ASCII or binary data (each sector is 2048 bytes). The ISO-9660 and Hi-Sierra standards specify that all volume data related through directory and file entries must start at Sector 16, leaving this gap of 32768 bytes where you may put binary data of your choice.Since the physical location of the System Area is guaranteed, you do not need any directory structure to access this data on the CD-ROM. One practical use is to put bootstrap code into this area, so a PC trying to boot from the CD-ROM can locate the boot record at physical location 0 of the CD-ROM.Like the Application Block field, the System Area field can accept the name of a DOS file on your hard disk to copy into Sectors 0 - 15 of the CD-ROM. RomMaker verifies that this file is smaller than 32768 bytes, the size of the System Area.FILL TO LOCATIONThis field is used for making multimedia CD-ROMs. Multimedia CD-ROMs have the audio component at a specified location following the data component. To successfully use the audio component, the retrieval software must know the location at which it begins. (Think what would happen if your software asked the CD-ROM player to play Mozart and some other type of music began to play!)The Fill To Location field tells RomMaker to pad the tape to the exact sector where the audio component beginsΓÇöeven if the data component does not take up all that space. You will then be able to ship a RomMaker DAT cartridge containing the data component as well as an audio tape containing your audio components to your mastering plant, which will insert the audio component immediately after this location. The Fill To Location field specifies this audio start location in terms of blocks, where each block contains 2048 bytes.RomMaker ensures that any data you put will fit into the area from the start of CD-ROM to the Fill To Location. If your files don't fit, RomMaker will stop during the pre-mastering phase of the CD-ROM process.MAXIMUM ROM SIZEThe maximum size of a CD-ROM is 664Mb, or 72 minutes and 2 seconds. You may wish to limit your CD-ROM to a smaller size, especially if your user population has older CD-ROM drives which often have problems reading areas past 60 minutes and 2 seconds. Newer drives do not have this problem, and can read the maximum potential of 660MB. If your files don't fit, RomMaker will stop during the pre-mastering phase of the CD-ROM process.LOGICAL BLOCK SIZEThis field is currently not editable; it is set to 2048 bytes.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>7</text>
</content>
<name>System Info</name>
<script></script>
</card>
card_33105.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>PUBLISHER INFOThis specifies the publisher of the CD-ROM; you can use up to 128 characters. Note that for many of these fields, the ISO 9660 and Hi-Sierra standards recognize only a limited character set, called the "A" character set: A to Z (uppercase only) 0 to 9 Space, ! , " , % , & , ', ( , ) , * , + Comma , - , . , / , : , ;, < , = , > , ?, _Thus the text "THE SMALL SCALE PUBLISHER & FRIENDS INC." would be allowed, while the text "PUBLISHER [LTD]" would not, since the [ and ] characters are not valid. RomMaker will signal an error if any invalid characters are entered in this field.If the publisher's name is longer than 128 characters, both the ISO and Hi-Sierra standards allow you to specify a filename in this field. This file must be placed on the CD-ROM at the root directory; it can contain as much information about the publisher as you need. To specify a file, the first character of this field must be an '_' character followed by the eight-character filename and the three-character file extension. For example, the text _PUBLISH.TXT in this field indicates that the publisher description is found in a file PUBLISH.TXT located in the root directory of the CD-ROM. RomMaker will signal an error if this file does not exist when you are premastering the CD-ROM.DATA PREPARER INFOThis specifies the person or entity that prepared the CD-ROM. You can use up to 128 characters. This is useful if you are using RomMaker to prepare CD-ROMs for other people such as where the Publisher is different than the Data Preparer. This field has the same attributes as the Publisher Info field (above), in that it can contain only characters from the "A" character set, and an underscore '_' followed by a filename can be used to extend the field contents.APPLICATION INFOThis specifies an identifier describing the application that is recorded on this CD-ROM; you can use up to 128 characters. This field has the same attributes as the Publisher Info field (above), in that it can contain only characters from the "A" character set, and an underscore '_' followed by a filename can be used to extend the field contents.COPYRIGHT FILEThis specifies a file to be placed in the root directory of the CD-ROM which contains a copyright statement regarding the contents of the CD-ROM. An ISO-9660 or Hi-Sierra filename consists of an eight-character filename and a three-character or less file extension, separated by the '.' character. Only the characters A-Z, 0-9 and '_' (called the "D" character set) can be used in the filename and extension. If you specify this file, RomMaker will check whether you have included this file in your root directory when you pre-master the CD-ROM.ABSTRACT FILEThis specifies a file to be placed in the root directory of the CD-ROM which contains an abstract statement regarding the contents of the CD-ROM. This is analogous to the abstract on the back cover of a book. Only the characters A-Z, 0-9 and '_' (called the "D" character set) can be used in the filename and extension. If you specify this file, RomMaker will check whether you have included this file in your root directory when you pre-master the CD-ROM.BIBLIOGRAPHIC FILEThis specifies a file to be placed in the root directory of the CD-ROM which contains bibliographic records interpreted according to standards agreed upon between the publisher and the user. This is analogous to the bibliographic summary found on the inside of a book, allowing the book to be classified by author and subject. Only the characters A-Z, 0-9 and '_' (called the "D" character set) can be used in the filename and extension. If you specify this file, RomMaker will check whether you have included this file in your root directory when you pre-master the CD-ROM.NOTE: The Hi-Sierra standard does not support the Bibliographic File field.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>6</text>
</content>
<name>Publication Info</name>
<script></script>
</card>
card_32838.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>DESKTOP MANAGEMENTThe Finder "Desktop" file is where the Macintosh keeps information about file and folder positions, window sizes and positions, which folders are open, etc. If you are making a CD-ROM that you know will be used only by Macintosh computers using System 7.0 or later, use the "System 7 only" option to save space on the CD-ROM. Otherwise it's safest to use the "System 6 and System 7" option.DESKTOP ITEMSThe Macintosh system has the ability to place files and folders on the desktop, that is, on the "background" area of the Macintosh screen, visually outside any disk or folder. When creating CD-ROMs for use by others, it's usually best to make sure any files and folders you have are not on the desktop, because it can be confusing to users if, when they insert a new disk, new items suddenly pop up on their desktop. However, RomMaker allows you to copy such items (using the "Copy" option will do this) if it encounters them in the ROM Content File. If, however, you want to make sure you don't inadvertently put any desktop items on your CD-ROM, just use the "Stop" option.If "Ignore" is used, any item found on the desktop during processing will be ignored, but RomMaker will continue processing the CD-ROM. Thus, if you want to temporarily hide a file or folder from RomMaker (without having to adjust the ROM Content File) you can just put it on the desktop and use the "Ignore" option.ICON MANAGEMENTRomMaker allows you to create a special "icon-only" image, using which you can set up your file, folder, and window positions just the way you want them. For more info on that topic, see help on the Make menu, under "Icon-only Image".The icon management section of the title file allows you to choose whether you want to use the icon database that the Make menu lets you create, and if so, how you want RomMaker to react when it finds a file or folder that doesn't have a corresponding entry in the icon database. You might want to use the "stop" option in this case, because it means that a file or folder was added to your source files between the making of the image and the making of the current CD-ROM.ALIAS MANAGEMENTThe Macintosh Finder, using System 7 or later, allows users to create "aliases" to files and folders. An alias represents the file or folder it was created with, in the sense that if you double-click an alias, the original file or folder will be opened. The alias is not really a copy of the item; rather it "points" to the original item in a way that the Macintosh file system can understand. For more info on aliases in general, see your Macintosh documentation.Use of aliases on CD-ROMs can be a great convenience for your System 7 users, because they can make tedious browsing of the CD-ROM folders unnecessary. RomMaker allows several options for dealing with aliases: if you use the "Resolve Aliases" option, RomMaker will automatically resolve aliases as it finds them. Resolving an alias means making it point to the item on the CD-ROM instead of to the original item on your hard disk or network. That way if a user double-clicks an alias on his CD-ROM, his Macintosh will be able to open the "original" on his CD-ROM, rather than trying to look on your hard disk or network, which of couse will probably not be available at the time.If the "Resolve Aliases" option is used, there is the possibility that RomMaker will encounter an alias whose original is not on the list of files to be copied on the CD-ROM. In that case, the alias is said to be "non-convertible". RomMaker allows you to either stop processing if such an alias is encountered, or ignore such aliases altogether (meaning they will not be copied to the CD-ROM).</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>5</text>
</content>
<name>Apple HFS Info</name>
<script></script>
</card>
card_32702.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">OLUME LABELThis label uniquely identifies the CD-ROM. It is analogous to a book's title on the front cover. Note that although this field can hold up to 32 characters, MS-DOS systems will recognize only the first 11 characters.ROM CONTENT FILEThis is the name of the file that tells RomMaker which files from your hard disk or network you want to put on the CD-ROM, and where they should go. This is an ASCII text file that you must create using a word processor or text editor (RomMaker's or your own). The complete format description allows for many options, but in general there is one line in the ROM Content File for each file or group of files you want to put on your CD-ROM.ROM STANDARDThis field tells RomMaker which directory structure and layout standard to use when making this CD-ROM. There are two recognized standards for specifying directory structure and layout for CD-ROMs: ISO 9660 and Hi-Sierra. The first standard to evolve, Hi-Sierra, was adopted across the United States. Later, the International Standards Organization (ISO) established ISO 9660 as an international standard, which is a superset of the Hi-Sierra format, and is more commonly used today. Unless you have a specific reason to use Hi-Sierra format, you should probably use Alternatively, RomMaker allows you to make CD-ROMs that use Apple HFS format, which preserves all desktop information such as window sizes and positions, icons, etc. for CD-ROMs meant to be used on Apple Macintosh systems.Finally, there is the combined Apple HFS/ISO 9660 format. This format allows one set of data files to be recognized by systems that read either HFS or ISO formats; in other words, you can create a single CD-ROM that can be read either by a Macintosh or MS-DOS system! The way this works is that RomMaker creates both HFS and ISO directory structures and points them to the same data files on the CD-ROM.FILENAME STANDARDDifferent ROM standards (see above) have different requirements for file and directory/folder names (collectively referred to as "filenames"). If the ROM Standard setting you are using refers to ISO 9660 or Hi-Sierra, it is possible that you could specify a file to be copied to the ROM image whose name is not allowed under that ROM Standard setting.The Filename Standard option tells RomMaker what to do in such a situation. You have the choice of three different filename standards for RomMaker to use, meaning that it will signal an error if it encounters a file whose name doesn't conform to the requirements of the current Filename Standard setting. Or you can also specify that RomMaker should attempt to automatically convert such names during processing (this may lead to duplicate filename errors, however, and should only be used if you thoroughly understand the consequences).Note that the Filename Standard setting applies only to file and directory names in an ISO partition; that is, it doesn't apply to Apple HFS ROMs, nor does it apply to the Apple HFS partition of an Apple HFS/ISO 9660 ROM.</span><span class="style2">MS-DOS</span><span class="style1">This option should be used with caution since it can produce a non-ISO-standard CD-ROM. In this case, all ISO 9660/Hi-Sierra filename enforcement is turned off and the original DOS filename is used on the CD-ROM. The CD-ROM thus produced is not ISO 9660/Hi-Sierra compliant. However, Microsoft extensions MSCDEX do allow you access to this CD-ROM since its volume structure still conforms to the standard. It's interchange capability with other systems is of course not guarantied. Occasionally you may even have problems reading this CD-ROM with MSCDEX.NOTE: Use this option only as a last resort and only if you clearly understand the nonstandard nature of the CD-ROM you are producing. This option also turns off the eight directory level limit on an ISO 9660/Hi-Sierra CD-ROM and allows you to use extension names in directories.If you invoke the Auto-Convert or DOS filename option, a warning will pop up each time you attempt to make a CD-ROM. A similar warning message stating the number of files that were converted or non-standard is also displayed upon termination of the processing.You can locate each filename which was either converted or non-standard by examining the log file produced when you make a CD-ROM. For each such file, an asterisk (*) is added to the attribute field to identify the file.</span><span class="style2">ISO 9660 Level 1</span><span class="style1">This option produces a CD-ROM that exactly conforms to the "D" standard, meaning that file and directory names must be made up of only the "D" character set, which allows only the characters A-Z, 0-9 and the '_' (underscore) character. In addition, file and folder names are limited to a 1-8 character root and a 0-3 character extension (like MS-DOS filenames).If RomMaker encounters an "illegal" file or directory name during processing, it will signal an error, unless the file/directory is explicitly dealt with in the ROM Content File (see), or the Auto-Convert option (see below) is in use.</span><span class="style2">ISO 9660/Hi-Sierra</span><span class="style1">This option produces a CD-ROM that exactly conforms to the "D" standard, meaning that file and directory names must be made up of only the "D" character set, which allows only the characters A-Z, 0-9 and the '_' (underscore) character. In addition, this option allows filenames up to 33 characters long, in contrast to the ISO 9660 Level 1 option which allows no more than 11 characters in a filename.If RomMaker encounters an "illegal" file or directory name during processing, it will signal an error, unless the file/directory is explicitly dealt with in the ROM Content File (see), or the Auto-Convert option (see below) is in use.</span><span class="style2">Auto-Convert</span><span class="style1">Checking this option invokes the filename conversion feature of the RomMaker that automatically converts any non-standard filenames to ISO 9660/Hi-Sierra-compliant names on the basis of a simple rule: Every character other than A-Z, 0-9 and '_' (underscore) in a filename is changed to an underscore character.For example, if Auto-Convert is used, the filename 'MY-FILE~.$$$' would get changed to 'MY_FILE_.___' . The CD-ROM produced after this conversion is ISO 9660/Hi-Sierra-compliant, since all the filenames use only the required "D" character set. If you use this option, you must take special care to verify that your software is operating correctly in all cases since it may be expecting the DOS filename and not the converted ISO 9660 filename.The most common error with this option is the "Duplicate file name found" error. This occurs if there is already a CD-ROM filename with the same name as that produced by automatic conversion. For example, suppose you had two files in a directory called MYFILE.___ and MYFILE.$$$ respectively. During automatic conversion the filename MYFILE.$$$ would get changed to MYFILE.___ resulting in a duplicate filename error. When this happens, RomMaker automatically serializes the duplicate filenames; i.e., in this case, the second occurrence of MYFILE.___ would be renamed MYFILE.__1, and so on.</span></text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>4</text>
</content>
<name>Volume Info</name>
<script></script>
</card>
card_32478.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The Title File is the primary document displayed when you use the Personal RomMaker. It specifies all the parameters that the RomMaker software needs to create CD-ROM images and write-once CD discs tailored to your exact needs. You can have several title filesΓÇöone for each CD-ROM "title" you regularly produce (although you can only work with one title file at a time).Each tab at the bottom of the title file window allows you to view and edit a different section of the title file; just click the tab to go to that section. The only required parameters in the entire title file are the "Volume Label" and "ROM Content File" (both in the "Volume Info" section); all other sections of the title file can be left blank or as the standard RomMaker values.Title files are created and saved using the standard Macintosh File menu.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>3</text>
</content>
<name>Title File</name>
<script></script>
</card>
card_32163.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">fter your Personal RomMaker software and hardware are properly installed, creating CD-ROMs and CD-ROM images is straightforward. RomMaker has many features and options, but there are really five basic steps in the process:</span><span class="style2">1) Prepare a Title File</span><span class="style1">The title file is what you are looking at when you start up RomMaker. It has several sections, each having a tab at the bottom, allowing you to move from section to section. RomMaker can only open one title file at a time.</span><span class="style6">To create, open, and save title files, use the "File" menu as you would for any Macintosh application.</span><span class="style1">The title file specifies what attributes the CD-ROM volume will have, such as its name, size, creation time, etc. Most important, it specifies a ROM Content File (see step 2). Editing the title file is easyΓÇölike filling out a big formΓÇöand almost all of the title file has standard settings, so you don't have to learn it all right away; you are required to specify only the name of the volume and the ROM content file.</span><span class="style2">2) Prepare a ROM Content File</span><span class="style1">This file is a list of all the files and folders that will be copied from your hard disk (or the network, or anywhere else you like) to the CD-ROM. You can copy an entire disk with a single line in the content file, or you can pick only specific files and folders to copy.</span><span class="style6">To create a ROM Content file, go to the "Volume Info" section of the title file. To learn about the format of the ROM Content file, see the help on "ROM Content File Format".</span><span class="style1"></span><span class="style2">3) Create a CD-ROM Image</span><span class="style1">RomMaker will use the Title and Content files you have prepared to create an "image" of the CD-ROM, that is, an exact copy on the RomMaker's own hard disk of what the actual CD will contain. You can use this image to test your CD content and format without having to create an actual CD, which can save a lot of time and money.</span><span class="style6">To create an image, use the "Make" menu.</span><span class="style1"></span><span class="style2">4) Test the CD-ROM Image</span><span class="style1">After creating an image, you can instruct RomMaker to have it mimic, or "emulate", an actual CD-ROM. This means that it will appear on the desktop just like the actual CD would if you inserted it into a CD-ROM drive. You can then open documents and applications, and run whatever tests you would use to verify whether the actual CD was satisfactory, only you'll be using the image instead. If the image is unsatisfactory, you can simply adjust the title and content files and make another imageΓÇöas many times as you like.</span><span class="style6">To test an image, use the "Emulate" menu.</span><span class="style1"></span><span class="style2">5) Make the Write-Once CD</span><span class="style1">After you have made an image that is satisfactory to you, you can create an actual Write-Once CD. The RomMaker will then copy the image on its internal hard disk onto the Write-Once CD to create a permanent CD-ROM, which you can use in any CD-ROM player that accepts the format you chose in the title file.</span><span class="style6">To make a write-once CD, use the "Make" menu.</span><span class="style1">There are, of course, many variations on the basic process. When testing the CD, RomMaker can mimic the characteristics of the CD-ROM drive of your choosing, and collect usage statistics so you can see what files are accessed on the CD-ROM during the test. You can make an image on a digital tape or a hard disk file instead of on RomMaker's hard disk. RomMaker also has special options for creating Apple Macintosh CD-ROMs, including the ability to adjust the layout of files, folders, and windows, by creating a special "icon-only" image, whose icons you can click and drag just as you would normally on the Macintosh. All these are ways in which RomMaker can tailor your CD-ROMs to your exact needs.</span></text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>2</text>
</content>
<name>Steps in Making a Write-Once CD</name>
<script></script>
</card>
card_31317.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Welcome to the Personal RomMaker!We hope you will find this to be the easiest, fastest, most flexible and trouble-free way you can find to create CD-ROMs. We who designed and wrote RomMaker are ourselves creators and users of CD-ROM products, and we have put into RomMaker the features and ease-of-use that we would demand from a product of its kind.RomMaker is designed for the experienced Macintosh user. You don't need to be a "techie", but if you are unfamiliar with the Macintosh system, you'll get more out of RomMaker if you at least go through the tutorial that came with your Macintosh, or spend some time learning and using Macintosh applications, or in some other way get some Mac experience. Or just have an "old hand" around to ask questions of. This will also help prevent your using up CD-ROM blanks unnecessarily, which, while not terribly expensive (around $40), aren't exactly free either!If this is your first experience creating a CD-ROM, we recommend that you read at least the next page: "Steps in making a Write-Once CD". This gives a brief overview of the typical sequence of operations, and give you a good idea of what to do next.</text>
</content>
<content>
<layer>background</layer>
<id>22</id>
<text>1</text>
</content>
<name>Introduction</name>
<script></script>
</card>
card_31032.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>IntroductionSteps in Making a Write-Once CDTITLE FILE Volume Info Apple HFS Info Publication Info System Info Date, Time, & Attributes Misc OptionsROM CONTENT FILEROMMAKER MENUS Make Emulate Examine Utilities</text>
</content>
<content>
<layer>card</layer>
<id>2</id>
<text>For information on any topic, click it.Note: While in RomMaker itself, you can click on any field label for help on that field.</text>
(2031)(1994).bin/pc/mac_file/vendor_d/rommaker/rommaker._he/BMAP_31868.png){kind=link}
(2031)(1994).bin/pc/mac_file/vendor_d/rommaker/rommaker._he/PATs.png){kind=link}